-------------------------------------------------------------------------------- To: Users of the Submit-Only versions of LoadLeveler 1.3.0 for non-AIX platforms. Subject: Installing Submit-Only versions of LoadLeveler 1.3.0 to your system running one of the following Operating Systems: HP-UX 9.0.x, HP-UX 10.x, IRIX 5.x, IRIX 6.x, and Solaris 2.x . -------------------------------------------------------------------------------- Overview -------- The steps for installation are as follows: 1. Set up a LoadLeveler userid, group, and filespace. 2. Receive the installation image. 3. Update various files for your configuration. 4. Repeat the installation process for each submit-only workstation in your pool. Disk Space Requirements ----------------------- The directories and the disk space used for each directory, after installation, are listed below. ------------------------------------------------------------ | Platform | Directory | Size | ------------------------------------------------------------ | IRIX | release directory | 5MB | | | (/usr/lpp/LoadL/sginfs_so) | | ------------------------------------------------------------ | HP-UX | release directory | 5MB | | | (/usr/lpp/LoadL/hpnfs_so) | | ------------------------------------------------------------ | Solaris | release directory | 6MB | | | (/usr/lpp/LoadL/solaris_so) | | ------------------------------------------------------------ NOTE 1 ------ LoadLeveler 1.3.x (Version 1, Release 3) is incompatible with LoadLeveler 1.2.x . The 1.3.0 submit-only binaries can only be used to submit jobs to (and query jobs at) a LoadLeveler cluster running Release 1.3.x level code. NOTE 2 ------ One of your main task as system administrator is to configure LoadLeveler. To configure LoadLeveler, you need to know what the configuration is and where it is located. Configuration information includes the following: - The LoadLeveler user ID and group ID . - The configuration directory. - The global configuration file. The default values are: - "loadl" is the LoadLeveler user ID and the LoadLeveler group ID . - The home directory of loadl is the configuration directory. - LoadL_config is the name of the configuration file. You can run your installation with these default values, or you can change any or all of them. To override the defaults, you must create a file called /etc/LoadL.cfg and update the following keywords in this file: - LoadLUserid Specifies the LoadLeveler user ID - LoadLGroupid Specifies the LoadLeveler group ID - LoadLConfig Specifies the full path name of the configuration file. Please refer to the document "Using and Administering LoadLeveler Release 3.0" for additional information on configuring LoadLeveler. In this note, we assume that you will be using the default configuration. NOTE 3 ------ LoadLeveler assumes a common name space. This means that a user must have the same user ID and group ID on all machines in a LoadLeveler cluster. 1. Set up Userid, Group, and Filespace -------------------------------------- This step must be done as root. 1. Create a userid named loadl and a group named loadl on the submit-only machine. You must use the same user id number for all LoadLeveler machines. The same is true for the group id. Include the loadl userid in the loadl group. Any other LoadLeveler administrators should also have their userids included in the loadl group. 2. Create the directory /usr/lpp/LoadL . Make "loadl" the owner of this directory: mkdir /usr/lpp cd /usr/lpp mkdir LoadL chown loadl LoadL chgrp loadl LoadL chmod 755 /usr/lpp /usr/lpp/LoadL 2. Receive the Installation Image --------------------------------- You must perform this step as root. It is assumed that the appropriate tar file has been copied to the /tmp directory. 1. Go to the /usr/lpp/LoadL directory: cd /usr/lpp/LoadL 2. Extract the files from the tar file by executing one of the following commands: tar -xvof /tmp/sgi_5_loadl_so.tar <-- IRIX 5.x tar -xvof /tmp/sgi_6_loadl_so.tar <-- IRIX 6.x tar -xvof /tmp/sol_2_loadl_so.tar <-- Solaris 2.x (SunOS 5.x) tar -xvf /tmp/hp_9_loadl_so.tar <-- HP-UX 9.0.x tar -xvf /tmp/hp_10_loadl_so.tar <-- HP-UX 10.x 3. Make "loadl" the owner of these files: chown -R loadl.loadl sginfs_so <-- IRIX chown -R loadl solaris_so <-- Solaris 2.x (SunOS 5.x) chgrp -R loadl solaris_so <-- Solaris 2.x (SunOS 5.x) chown -R loadl hpnfs_so <-- HP-UX chgrp -R loadl hpnfs_so <-- HP-UX 3. Update various files for your configuration ---------------------------------------------- This step must be performed as loadl. Ensure that your HOME environment variable is set to loadl's home directory. 1. Create a number of symbolic links: cd $HOME ln -s /usr/lpp/LoadL/sginfs_so/bin bin <-- IRIX ln -s /usr/lpp/LoadL/sginfs_so/lib lib <-- IRIX ln -s /usr/lpp/LoadL/solaris_so/bin bin <-- Solaris 2.x ln -s /usr/lpp/LoadL/solaris_so/lib lib <-- Solaris 2.x ln -s /usr/lpp/LoadL/hpnfs_so/bin bin <-- HP-UX ln -s /usr/lpp/LoadL/hpnfs_so/lib lib <-- HP-UX 2. Copy the LoadL_config.so , LoadL_admin, and LoadL_config.local.so files from the release directory to the loadl home directory and rename them as LoadL_config, LoadL_admin, LoadL_config.local . cd $HOME For IRIX systems: cp /usr/lpp/LoadL/sginfs_so/samples/LoadL_admin LoadL_admin cp /usr/lpp/LoadL/sginfs_so/samples/LoadL_config.so LoadL_config cp /usr/lpp/LoadL/sginfs_so/samples/LoadL_config.local.so LoadL_config.local For Solaris 2.x systems: cp /usr/lpp/LoadL/solaris_so/samples/LoadL_admin LoadL_admin cp /usr/lpp/LoadL/solaris_so/samples/LoadL_config.so LoadL_config cp /usr/lpp/LoadL/solaris_so/samples/LoadL_config.local.so LoadL_config.local For HP-UX systems: cp /usr/lpp/LoadL/hpnfs_so/samples/LoadL_admin LoadL_admin cp /usr/lpp/LoadL/hpnfs_so/samples/LoadL_config.so LoadL_config cp /usr/lpp/LoadL/hpnfs_so/samples/LoadL_config.local.so LoadL_config.local 3. Edit the LoadL_config, LoadL_admin, and LoadL_config.local files so that the information they contain is consistent with the state of your existing LoadLeveler cluster. In a well managed LoadLeveler cluster, every machines in the cluster should see the same LoadL_config and LoadL_admin files. This can be very simply implemented via NFS. Anything specific to a given machine should be in the LoadL_config.local file. So, instead of creating special versions of LoadL_config and LoadL_admin files for a submit-only machine, a better strategy would be to modify the existing LoadL_config and LoadL_admin files of your cluster so that they include information about the new submit-only machine. After appropriate modifications have been made to these files, they should be made available to the submit-only machine either via NFS mounting or as duplicate copies. - LoadL_admin: You have to add the name of this submit-only machine to the list of machines. If the name of this machine is "so_ll3" you must add the following stanza to the file: so_ll3: type = machine schedd_host = false submit_only = true Since a submit-only machine does not have a "job queue", you want to make sure that at least one machine in the cluster is a public scheduler. A public scheduler is a machine that runs the the LoadL_schedd daemon and has the schedd_host keyword set to true (schedd_host = true) and submit_only keyword set to false (submit_only = false). Jobs submitted from a submit-only machine will enter the "job queue" of one of the public schedulers. - LoadL_config.local : For a submit-only machine this file should at the minimum contain the following: ARCH = SPARC Arch: "$(ARCH)" SCHEDD_RUNS_HERE = FALSE START_DAEMONS = FALSE Replace SPARC by HPPAR if the machine runs HP-UX. Replace SPARC by SGI if the machine runs IRIX. NOTE: After making changes to the LoadL_admin, LoadL_config, and LoadL_config.local files you have to execute the command: llctl -g reconfig so that the changes become effective. This command must be executed by a LoadLeveler administrator on a "regular" LoadLeveler machine. It is not necessary to execute this command on a submit-only machine. 4. Copy the Xloadl_so Resource file of "xloadl_so" from the lib subdirectory of the release directory to /usr/lib/X11/app-defaults or to /usr/openwin/lib/app-defaults. You must have root authority to copy files into these directories. "xloadl_so" is the submit-only version of "xloadl", the LoadLeveler Motif-based Graphical User Interface. 5. Add /usr/lpp/LoadL/sginfs_so/bin to the PATH environment variable if you are running IRIX. Add similar strings to your PATH environment variable if you are running other Operating Systems. 6. From the submit-only machine you can now submit jobs, query job status, and camcel jobs with the commands: "llsubmit", "llq", "llcancel". The same functions can also be done by using "xloadl_so", the submit-only Graphical User Interface. 4. Installing on Other Machines in the Pool ------------------------------------------- Repeat the previous steps for each machine in the pool. If the release directory can be mounted using NFS, you do not have to receive the installation image. You can mount the release directory onto the machine.